Methods and systems for autonomous vehicle refueling

ABSTRACT

A method at an autonomous vehicle for signaling a refueling attendant, the method including confirming that the autonomous vehicle is proximal to a refueling station; providing a signal to the refueling attendant; waiting for refueling to commence; and if, after a threshold period, refueling has not commenced, repeating the providing the signal.

FIELD OF THE DISCLOSURE

The present disclosure relates to autonomous vehicles, and in particularrelates to the refueling of autonomous vehicles.

BACKGROUND

Autonomous vehicles are likely to become widely used in coming years.Such autonomous vehicles may be used for many purposes, includingautonomous deliveries, autonomous taxicabs, vehicle sharinginfrastructures in which the vehicle relocates itself in between users,among other options.

Autonomous vehicles would be powered through one or more of a variety ofsources. Options may include gasoline, diesel, or electric power, amongothers. It is foreseen that different autonomous vehicles would usedifferent types of power for various reasons. For example, gas or dieselwould allow further travel with today's technology and provides theneeded power for hauling heavy loads.

However, if the autonomous vehicle has no passenger or other personassociated with it, then refueling may be difficult. For example, in anautonomous delivery vehicle, a company would unlikely want to hiresomeone to periodically fill up the vehicle with gasoline, as this wouldcreate an added expense.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be better understood with reference to thedrawings, in which:

FIG. 1 is a block diagram showing an example system for scheduling avehicle at a refueling station;

FIG. 2 is process diagram showing a process at a server for maintainingrefueling station information;

FIG. 3 is a process diagram showing a process at an autonomous vehiclefor scheduling an appointment at a refueling station using a centralserver;

FIG. 4 is a process diagram showing a process at a central server forproviding information to an autonomous vehicle;

FIG. 5 is a process diagram showing a process at an autonomous vehiclefor selecting a refueling station and scheduling an appointment;

FIG. 6 is a process diagram showing a process at a refueling station orserver for a refueling station for responding to requests from vehicles;

FIG. 7 is a process diagram showing a process at an autonomous vehiclefor signaling an attendant that the vehicle has arrived at a refuelingstation and needs refueling;

FIG. 8 is a block diagram showing a short-range communications system ata refueling station for alerting an attendant;

FIG. 9 is a block diagram showing near field communications readers andtags for securing a fueling port;

FIG. 10 is a block diagram showing near field communications readers andtags for providing payment for fueling;

FIG. 11 is a process diagram showing a process at a refueling stationfor providing payment for fueling; and

FIG. 12 is a block diagram showing an example computing device capableof being used in accordance with the systems and methods of the presentdisclosure.

DETAILED DESCRIPTION

The present disclosure provides a method at an autonomous vehicle forsignaling a refueling attendant, the method comprising: confirming thatthe autonomous vehicle is proximal to a refueling station; providing asignal to the refueling attendant; waiting for refueling to commence;and if, after a threshold period, refueling has not commenced, repeatingthe providing the signal.

The present disclosure further provides a computing device associatedwith an autonomous vehicle for signaling a refueling attendant, thecomputing device comprising: a processor; and a communicationssubsystem, wherein the computing device is configured to: confirm thatthe autonomous vehicle is proximal to a refueling station; provide asignal to the refueling attendant; wait for refueling to commence; andif, after a threshold period, refueling has not commenced, repeat theproviding the signal.

The present disclosure further provides a computer readable medium forstoring instruction code for signaling a refueling attendant, which whenexecuted by a processor of a computing device associated with anautonomous vehicle cause the computing device to: confirm that theautonomous vehicle is proximal a refueling station; provide a signal tothe refueling attendant; wait for refueling to commence; and if, after athreshold period, refueling has not commenced, repeat the providing thesignal.

One issue for autonomous vehicle refueling relates to payment for therefueling. In accordance with one embodiment of the present disclosure,payment may be made using short range communications, such as near fieldcommunications (NFC). For example, an NFC payment reader may beintegrated into a gas line nozzle and a payment card or chip may beincluded inside a gas door. In this case, when the gas nozzle isinserted far enough into the gas door, the reader and chip may make aconnection and payment may be made upon verification of the credentials.Such system avoids a second, separate, system to make a connection forpayment purposes.

A further issue for autonomous refueling involves the actual pumping ofthe fuel or the attachment of the fuel mechanism. In this case, anattendant needs to know when an autonomous vehicle is present and readyfor refueling. This is especially true since most stations today areself-serve.

In order to accomplish refueling using an attendant, in accordance withone embodiment of the present disclosure, an autonomous vehicle may havea signaling mechanism such as a flashing light or audio feature in orderto get an attendant's attention. In alternative embodiments, a wirelessconnection system may be provided in which a device inside an attendantstation or associated with an attendant is signaled when a vehicle isready to be refueled. Such signaling system can also schedule vehiclesfor refueling to avoid several vehicles arriving at the same time.

A further issue for autonomous vehicle refueling involves ensuring avehicle is receiving the correct fuel from a correct vendor and makingthe payments to the correct vendor. For example, the owners of theautonomous vehicle do not want to be making payments to anyone that haspurchased a gas nozzle and accepting payment for filling the vehicle ofsomething other than the correct fuel. In order to avoid such situation,in one embodiment of the present disclosure, a short-range communicationsystem, such as an NFC reader chip, may be used at the fueling door. Inthis case, when a communication connection is made, a vehicle may issuechallenge and a response from the vendor may be received in order toverify the identity of the vendor. If the response is verified, afueling door may be opened and payment may be made. Otherwise the fueldoor is kept closed and payment is not made.

In one embodiment, the short-range communications system may reuse thepayment system on a gas nozzle. Other embodiments may include a tap of aseparate card or module before the fuel door is opened.

Reference is now made to FIG. 1 , which shows an example architecture inaccordance with the embodiments of the present disclosure. Inparticular, in the embodiment of FIG. 1 , a vehicle 110 is an autonomousvehicle. As provided in more detail below, vehicle 110 includes aprocessor and a communications subsystem which allows it to communicate,for example through a access point or base station 120 with Internet122. In other embodiments, vehicle 110 may communicate with Internet 122through any short or long range communications system, includingsatellite, cellular, Wi-Fi, NFC, among other options.

Vehicle 110 may be related to a server 130. For example, if vehicle 110is a delivery vehicle, server 130 may be a fleet management server whichmanages a fleet of such autonomous vehicles.

In accordance with the embodiments of the present disclosure, vehicle110 realizes that it needs fuel. For example, if vehicle 110 is a gas ordiesel powered vehicle, it may have sensors within the gas tank, andonce a level of gas falls below a threshold, the vehicle 110 may startsearching for gas stations at which to refuel. If vehicle 110 isconversely an electric vehicle, it may have monitors on the battery todetermine when the battery level falls below a threshold level.

Once the threshold for refueling is reached, vehicle 110 may try tolocate a gas station or other refueling station. For example, in theembodiment of FIG. 1 , refueling stations 140 and 142 are shown in thevicinity of vehicle 110.

In accordance with the embodiment of FIG. 1 , refueling stations 140 and142 may communicate over Internet 122 with various entities, including aserver 150. The communications between the refueling station 142 andInternet 122 may, for example, be through a wired connection such asEthernet, or may be over a wireless connection. For example, refuelingstation 140 may communicate using a base station 144.

Server 150 may be a server or combination of servers that providefunctionality for the refueling of autonomous vehicles. In this case, ifrefueling stations 140 and 142 are capable of handling autonomousvehicles, they may register with server 150 and may further provide aserver 150 with updates as to the status and availability for refuelingat the station.

Similarly, vehicle 110 may register with server 150 and may requestinformation with regard to refueling stations in its vicinity.

For example, reference is now made to FIG. 2 . In the embodiment of FIG.2 , a server such as server 150 starts the process at block 210 andproceeds to block 212 in which information from one of a plurality ofrefueling stations is received. For example, refueling station 140 maysignal to server 150 that it is capable of handling autonomous vehicles,that it is capable of handling autonomous vehicles for limited timeperiods, that it is currently servicing other vehicles and does not havea pump for an autonomous vehicle, details about the station such aswhere pumps are located and those best suited to autonomous vehicles,among other information.

The process may then proceed to block 214 in which the information aboutthe station sending the message received at block 212 is updated.

The process then proceeds to block 220 and ends.

Therefore, in accordance with the embodiment of FIG. 2 , a server suchas server 150 may keep a record of a plurality of refueling stations andthe capabilities of such refueling stations to handle autonomousvehicles.

Referring to FIG. 3 , a vehicle such as vehicle 110 starts the processat block 310 and proceeds to block 312 in which a check at the vehicleis made to determine whether a threshold for refueling has been met. Forexample, if the gas tank on the vehicle is less than one quarter full orif the battery on the vehicle indicates less than 50 km remaining thenthe check at block 312 may be met. Otherwise, the process proceeds backto block 312 until the threshold is met.

In other examples the threshold may be combined with other criteria. Forexample, for an autonomous taxi, the threshold may be met only when thefuel level is below a value and there are no passengers. In this casethe threshold fuel level may be set to a higher value to allow forpassenger trips to be completed.

In other cases, multiple thresholds may exist. For example, when anautonomous taxi detects it is below ⅓ of a tank it may check and deferrefueling if a passenger is present. However, if the fuel readingreaches ⅛ of a tank, refueling may be initiated, regardless of whether apassenger is present.

In other cases, refueling may occur, regardless of the amount of fuelcurrently in the vehicle, in preparation for a trip. For example, a taximay be ⅞ full, but at the end of the day may refuel anyway to preparefor the next day. Similarly, an autonomous delivery vehicle may refuelbetween deliveries, regardless of fuel level.

Other examples and thresholds are possible, and the above examples areprovided for illustration only.

Once the threshold is met, the process proceeds to block 314 in whichthe vehicle 110 requests refueling station information from server 150.The request at block 314 may ask for either a single station or may askfor a variety of choices of stations within a geographic boundary area,for example. The request at block 314 may include the position of thevehicle 110, along with identifiers.

Further, in some cases, the request at block 314 may include othersupplemental information. For example, the vehicle 110 may belong to afleet that has an agreement with a particular owner or brand ofrefueling stations and in this case, the request at block 314 mayindicate a preference for specific brands of stations. In other cases,the request at block 314 may indicate a type of fuel desired, the gradeof fuel desired, among other such information.

The vehicle 110 then receives information at block 320 about one or morestations that can service the vehicle. In some cases, the informationmay include supplementary information about the station, such aslocation of a particular pump that the vehicle should use.

Based on the information received at block 320, the process proceeds toblock 322 in which the vehicle may confirm an appointment for refuelingwith a station chosen from the received station information at block320.

The process then proceeds to block 330 and ends.

At the server side, a process is shown with regard to FIG. 4 . In theprocess of FIG. 4 , the process starts at block 410 and proceeds toblock 412 in which a request from a vehicle is received. As indicatedwith regard to block 314, the request may include information about thevehicle, the types of stations that the vehicle would like to use, thegeographic area of the vehicle, the grade of fuel of the vehicle, howfar the vehicle can travel with its remaining fuel, or otherinformation. However, such examples are not limiting, and in other casesmore or less information may be provided in the request received atblock 412

From block 412 the process proceeds to block 420 in which theinformation about available stations is retrieved. This may be done, forexample, utilizing a database search and using criteria received in themessage at block 412.

In some cases, if there are no stations within the vicinity of thevehicle matching all of the criteria of message 412, stations that matcha high percentage of the criteria may be returned. In other cases,certain types of criteria may be considered essential, such as a fueltype, while other criteria may be optional, such as a brand of fuelingstation. Based the provided criteria, results matching as closely aspossible may be obtained.

From block 420 the process proceeds to block 430 in which the retrievedinformation is then sent back to the vehicle. Other information such asprice of fuel, estimated wait time, or traffic conditions or hazardsbetween the current location of the vehicle and the station, among otherpossible supplemental information, could be provided in the message ofblock 430.

From block 430 the process proceeds to block 440 and ends.

Therefore, in accordance with processes of FIGS. 2 to 4 , a centralserver 150 may keep a record of refueling stations, their geographiclocations, their capabilities, their scheduling, among other informationand may then match requests from vehicles 110 with the appropriatestations. The server may provide a list of one or more availablestations back to a vehicle 110 upon request. In this case, if thevehicle receives more than one station it may make a selection based onvarious criteria including the geographic locations, the price of thefuel, the owner of the station, historical data on previous service,among other options.

Referring again to FIG. 1 , instead of a central server providinginformation with regard to refueling stations, in some embodimentsvehicle 110 may query stations directly or through the use of a fleetmanagement server 130.

Reference is now made to FIG. 5 , which illustrates a process at avehicle for locating and booking an appointment with a station. Theprocess starts at block 510 and proceeds to block 512 in which adetermination is made on whether or not the vehicle needs to refuel. Forexample, the refueling may be based on a threshold level of fuel orcharge the vehicle has remaining. As with the check at block 312 of FIG.3 , other information such as passenger status, upcoming driving needed,time of day, among other information, could also be used in the check ofblock 512.

If, at block 512, it is determined that the threshold is not met, thenthe process may continue to loop back to block 512 until the thresholdis met.

From block 512, the process proceeds to block 520 in which a refuelingstation is located. The location of the station may be based on variouscriteria including the current location of the vehicle, as well as thelocation and availability of the refueling stations. For example,vehicle 110 may keep a database of refueling stations that serveautonomous vehicles and may then refer to this database to find acandidate station. In other embodiments, vehicle 110 may query server130 for available stations in the geographic location to find acandidate station and may receive from server 130 such candidatestations. Other options for determining a candidate refueling stationare possible.

From block 520, once a candidate station has been located the processproceeds to block 522 in which a request is sent to the candidatestation. Such request may include various information, including but notlimited to an indication that the vehicle is an autonomous vehicle, thetype of fuel required, and/or the time window for the refuelingrequested.

In response to the message sent at block 522, the vehicle receives aresponse at block 524. The response might contain information such asavailability, whether the station has the correct type of fuel orcharging station, the price of the fuel, or other such information.

A processor on a vehicle 110 may then analyze the response and at block530 determine whether the candidate station is appropriate and whetherit should therefore be used for refueling. For example, if the responsereceived at block 524 indicates that the station is currently notavailable, that it does not have the appropriate fuel, that it cannotaccommodate an autonomous vehicle for a certain time period, or that theprice of fuel is higher than a threshold value, the process may proceedfrom block 530 back to block 520 in which a different candidate stationmay be located.

Conversely, if at block 530 it is determined that the station can meetthe autonomous vehicle's needs, the process may proceed to block 540 inwhich a appointment with the refueling station may be confirmed. Theprocess then proceeds to block 542 and ends.

Reference is now made to FIG. 6 , which shows a process at the refuelingstation. The process of FIG. 6 starts at block 610 and proceeds to block612 in which the request from the vehicle is received.

The process then proceeds to block 620 in which a response is generatedbased on the contents of the request. For example, if the request asksfor a particular time window, for the capabilities with regard toautonomous vehicles, for a particular fuel type or grade, among otherinformation, the response generated at block 620 may be based on thecapabilities of the refueling station, previous scheduling at therefueling station, prices at the refueling station, among otherinformation.

The response is then sent at block 620 and the process proceeds to block630 and ends.

While the embodiment above shows the query to the actual refuelingstation, in some cases, the refueling station may be served by a serverfor either the refueling station itself or for a plurality of refuelingstations. For example, a particular vendor may have multiple refuelingstations but have a single server providing information back to avehicle based on the query. Other examples are possible.

A vehicle may then arrive at a refueling station. The station may beaware of the vehicle's arrival based on the appointment confirmed atblocks 322 or 540. However, in some embodiments the process of FIGS. 2to 5 may be omitted and a vehicle may arrive unannounced at a refuelingstation.

Reference is now made to FIG. 7 in which a process from a vehicle'sperspective is provided with regard to the arrival at the refuelingstation. In particular, the process starts at block 710 and proceeds toblock 712 in which a processor on the vehicle confirms that the vehiclehas arrived at the refueling station. Such confirmation may be based ona location sensor on the vehicle. For example, if the vehicle is withina geographic boundary of the refueling station, this may indicate thatthe vehicle is proximal to the station and provide confirmation. Inother embodiments, the confirmation at block 712 may be a visualconfirmation based on characteristics of the refueling station. In otherembodiments, the refueling station may provide a short-rangecommunication signal that may be detected by the vehicle. Other examplesare possible.

Once the vehicle confirms it has arrived at the refueling station, theprocess proceeds to block 720 in which a signal is provided to anattendant that the autonomous vehicle needs to be refueled.

In accordance with one embodiment of the present disclosure, the signalmay be a visual signal to the attendant. For example, this may include alight on the top of the vehicle to signal an attendant, which may startto flash when the vehicle needs to be refueled. The signal may furtherinclude the flashing of the front or brake lights of the vehicle. Othervisual signals are possible.

In other embodiments, the signal may be an audio signal. For example,the vehicle may honk its horn or provide an audible signal through aspeaker system on the vehicle.

In other embodiments, the audio and visual signals may be combined toget the attention of the attendant.

In still further embodiments, the signal may be a wireless signal to theattendant. For example, the attendant station may include a receiverwhich may provide audio, visual or sensory signals to an attendant thatthe autonomous vehicle has arrived.

For example, reference is now made to FIG. 8 . In the embodiment of FIG.8 , a vehicle 110 may see a short-range communication system associatedwith the refueling station. In particular, such short-rangecommunication system may have an access point 810 which the vehicle 110may register with. Upon registration, a station receiver 820 may beprovided with the signal that the registration of the vehicle hasoccurred and may therefore provide an audio, visual or sensory alert toan attendant at the station.

In one embodiment, station receiver 820 may be fixed. In otherembodiments, the station receiver may be a mobile device carried by anattendant such as mobile device 830. In some embodiments, mobile device830 may register to receive alerts. For example, the mobile device 830may have an application that registers to receive alerts in oneembodiment. The registration may include a connection to a particularserver in one case. In other cases, registration may include a nearfield communication (NFC) signal. For example, the mobile device may useNFC to register with the station receiver 820 in order to register thedevice to receive alerts. Other options are possible.

Rather than a short-range communication system, in other cases, vehicle110 may register with the station receiver 820 using cellular signals orother access points. For example, the station receiver 820 may registerwith a particular server and vehicle 110 may look up the address of thestation receiver utilizing a similar server or through its vehicle orfleet management server 130.

Other options are possible.

Referring again to FIG. 7 , once the signal is provided to the attendantat block 720, the process proceeds to block 722 in which a delay isintroduced. After the delay, the process proceeds to block 730 in whicha check is made to determine whether the attendant has started refuelingthe vehicle. For example, as described below, the refueling may bedetected by the fuel nozzle being held in proximity to the fuel door.

If the attendant has not started refueling the vehicle then the processproceeds back to block 720 in which the signal is provided again to theattendant. In this way, the signal may be provided with a periodic delayin order to get the attendant's attention.

Once the attendant has started refueling the process proceeds to block740 and ends.

In some cases, multiple vehicles may arrive at a refueling station atthe same time. In this case, the signal provided at block 720 may berequest for fueling to the refueling station and the response from thestation receiver may indicate that the vehicle has been placed in aqueue and needs to wait. For example, a designated waiting area may beprovided at the station.

Once the queue has reached the vehicle, the station receiver 820 mayprovide a signal to the vehicle to move to a pump. In this case, ratherthan proceeding to block 730 in which a check is made whether theattendant has started refueling, the signal from the receiver 820 may besufficient to indicate that the attendant is aware of the vehicle.

Other options are possible.

Once the attendant has been signaled, refueling may begin. In oneembodiment, security at the vehicle may be used to ensure thatfraudulent transactions are not occurring. In particular, the vehiclemay wish to avoid someone other than a legitimate attendant at thestation from accessing the fuel system in order to retrieve payment andalso to avoid the vehicle being filled with something other than thedesired fuel. In this case, security may be provided at the vehiclerefueling port. Reference is now made to FIG. 9 .

In the embodiment of FIG. 9 , a vehicle 110 includes an NFC reader 910.NFC reader 910 may be on or around the fuel port on the vehicle. In thiscase, a system may be provided in which the door to the refueling portmay be locked until an NFC challenge is successfully completed

Specifically, in one embodiment, an attendant at a refueling station mayhave an NFC enabled smart card 912 which includes an NFC chip associatedwith it. The attendant may, prior to fueling, place the NFC enabledsmart card 912 in the vicinity of the NFC reader 910. The NFC reader 910may then provide a challenge to the NFC enabled smart card 912 and mayreceive a response back. The response may then be verified prior to thefuel door being opened.

For example, in one embodiment, the NFC reader may provide a challengeto the NFC enabled smart card 912 and may compare the response with anexpected response. For example, reader 910 would generate a randomnumber and send it to the NFC enabled smart card 912. The NFC enabledsmart card 912 would sign the number (or “challenge”) with a private keyand then the reader 910 would verify the challenge with a public key.Thus, in some embodiments, the challenge in response may be based onencryption/signing or security algorithms.

In other embodiments, an NFC enabled smart card 920 may be associatedwith a fuel nozzle 922. Thus, instead of using a separate card, the NFCenabled smart card 920 may be placed in the vicinity of NFC reader 910by holding the fuel nozzle close to the vehicle. NFC enabled smart card920 may similarly be challenged or asked to provide information back toreader 910, as described above with regards to the NFC enabled smartcard 912.

In other embodiments, other locations for an NFC enabled smart card arepossible.

In still further embodiments, those skilled in the art will appreciatethat other short range communications technologies instead of an NFCenabled smart card could be utilized to verify the fuel provider.

While the above challenges may be passive, in some cases, information,for example based on the booking or based on codes exchanged between thevehicle and the station, may be utilized as part of the challenge.

Once the NFC reader 910 verifies the information at either NFC enabledsmart card 912 or 920, the fuel door may be opened at the vehicle 110.

In other embodiments, the fuel door of the vehicle may be opened withoutrequiring short range security verification.

Once the fuel door is opened, payment for the fueling may occur.Reference is now made to FIG. 10 .

In the embodiment of FIG. 10 , a reader 1012 can be included on the fuelnozzle 1010. In particular, in the example of FIG. 10 , the reader 1012is shown at the front of the fuel nozzle handle. However, in otherembodiments it might be somewhere else on fuel nozzle 1010.

The reader 1012 on the fueling nozzle 1010 may then be placed inproximity to the fuel port when fueling nozzle 1010 is inserted into thefuel line on vehicle 110.

In this case, an NFC enabled payment card 1020 associated with thevehicle may act as an NFC chip for the payment transaction as describedbelow. For example, the NFC enabled payment card 1020 may be providednear the fuel port of vehicle 110.

In other embodiments, other locations for an NFC enabled payment cardare possible.

In still further embodiments, those skilled in the art will appreciatethat other short range communications technologies instead of an NFCenabled payment card could be utilized to verify the fuel provider.

Reader 1012 may then interact with the NFC enabled payment card 1020 toobtain payment. Thus, when the fuel nozzle is inserted far enough intothe fuel line of the vehicle, the reader and NFC enabled payment cardmay make a connection and payment may be made.

In one embodiment, the payment card 1020 may not be activated until afuel door is opened or authentication of the vendor has been completed.This prevents NFC communications prior to the authentication foradditional security for the payment system.

In other embodiments, the payment card 1020 may be located in a layer ofmaterials that prevents the card from being read. For example, the fueldoor may be lined or comprise a material to ensure the card cannot beread without access to inside of the fuel door. Such system assumes thatthe fuel door has a locking mechanism to prevent access until an eventsuch as a vendor authentication has occurred. Such embodiment preventsNFC communications while the fuel door is closed and thereby providesadditional security for the payment system by avoiding someone walkingby the vehicle and scamming the payment card 1020.

Payment may be based on a challenge and response and may, for example,include a prepayment prior to refueling. The prepayment can then beconverted into a payment once fueling has finished and the amount offuel has been registered. In some embodiments, the payment or prepaymentmay be done through the booking system instead.

Similarly, for electric vehicles, the NFC enabled payment card 1020 canbe associated with the recharging port and the reader 1012 may be partof the charging cable. In this case, payment can be made in a similarway to the gas payment system described above.

Once fueling has completed, a payment system for the station cancomplete the transaction by identifying the amount of fuel or durationof charge provided, and thereby complete the transaction.

In accordance with one embodiment of the present disclosure, vehicle 110may also have sensors to detect the amount of fuel added to the vehicle.This may be either the duration and amount of charge added or the amountof gasoline or diesel fuel added to the vehicle. Such detection can beused to compare the charges made against the charges expected, and couldlead to dispute resolution mechanisms in cases of large discrepancies.

Reference is now made to FIG. 11 , which shows a process from therefueling station's perspective. The process of FIG. 11 starts a block1110 and proceeds to block 1112 in which the NFC reader associated withthe fuel nozzle provides a payment challenge to the vehicle. Asdescribed above, the challenge may be made to payment card that isassociated with the fuel tank of the vehicle.

The reader then receives a response a block 1120 and the response isverified at block 1122.

Once the response is verified, a payment authorization may be made atblock 1130. For example, such payment authorization may includecommunications between a refueling station and a bank or credit cardcompany based on the payment information received at block 1120. Thepayment may, for example, be a preauthorization for a certain dollaramount. Further, in some cases a maximum amount may be configured basedon an amount of fuel needed and the price of the fuel.

The process then proceeds to block 1140 in which the fueling occurs.

Once fueling is completed or the maximum dollar amount has been reached,the process then proceeds to block 1150 in which the payment isfinalized. In particular, the authorized payment may be for a maximumamount of fuel that is allowed to be transferred to the vehicle but thefueling at block 1140 may be less than this amount. Therefore, paymentwill be based on the amount of fuel actually transferred to the vehicleand the payment may be finalized based on this actual amount at block1150.

From block 1150 the process proceeds to block 1160 and ends.

The above description therefore provides for methods and systems forrefueling autonomous vehicles.

The autonomous vehicle 110, as well as server 130, server 150,processors at fueling stations 140 and 142, receiver station 820, device830 may user any computing device. For example, one simplified computingdevice that may perform the embodiments described above is provided withregards to FIG. 12 .

In FIG. 12 , computing device 1210 includes a processor 1220 and acommunications subsystem 1230, where the processor 1220 andcommunications subsystem 1230 cooperate to perform the methods of theembodiments described herein.

The processor 1220 is configured to execute programmable logic, whichmay be stored, along with data, on the computing device 1210, and isshown in the example of FIG. 12 as memory 1240. The memory 1240 can beany tangible, non-transitory computer readable storage medium, such asoptical (e.g., CD, DVD, etc.), magnetic (e.g., tape), flash drive, harddrive, or other memory known in the art. In one embodiment, processor1220 may also be implemented entirely in hardware and not require anystored program to execute logic functions.

Alternatively, or in addition to the memory 1240, the computing device1210 may access data or programmable logic from an external storagemedium, for example through the communications subsystem 1230.

The communications subsystem 1230 allows the computing 1210 tocommunicate with other devices or network elements. The communicationssubsystem 1230 may use one or more of a variety of communications types,including but not limited to cellular, satellite, Bluetooth™, Bluetooth™Low Energy (BLE), Wi-Fi, wireless local area network (WLAN), wirelesspersonal area networks (WPAN), near field communications (NFC), ZigBeeor any other IEEE 802.15 low power technology, wired connections such asEthernet or fiber, among other options.

As such, a communications subsystem 1230 for wireless communicationswill typically have one or more receivers and transmitters, as well asassociated components such as one or more antenna elements, localoscillators (LOs), and may include a processing module such as a digitalsignal processor (DSP). As will be apparent to those skilled in thefield of communications, the particular design of the communicationsubsystem 1230 will be dependent upon the communication network orcommunication technology on which the sensor apparatus is intended tooperate.

Communications between the various elements of the computing device 1210may be through an internal bus 1260 in one embodiment. However, otherforms of communication are possible.

The embodiments described herein are examples of structures, systems ormethods having elements corresponding to elements of the techniques ofthis application. This written description may enable those skilled inthe art to make and use embodiments having alternative elements thatlikewise correspond to the elements of the techniques of thisapplication. The intended scope of the techniques of this applicationthus includes other structures, systems or methods that do not differfrom the techniques of this application as described herein, and furtherincludes other structures, systems or methods with insubstantialdifferences from the techniques of this application as described herein.

While operations are depicted in the drawings in a particular order,this should not be understood as requiring that such operations beperformed in the particular order shown or in sequential order, or thatall illustrated operations be performed, to achieve desirable results.In certain circumstances, multitasking and parallel processing may beemployed. Moreover, the separation of various system components in theimplementation descried above should not be understood as requiring suchseparation in all implementations, and it should be understood that thedescribed program components and systems can generally be integratedtogether in a signal software product or packaged into multiple softwareproducts. In some cases, functions may be performed entirely in hardwareand such a solution may be the functional equivalent of a softwaresolution

Also, techniques, systems, subsystems, and methods described andillustrated in the various implementations as discrete or separate maybe combined or integrated with other systems, modules, techniques, ormethods. Other items shown or discussed as coupled or directly coupledor communicating with each other may be indirectly coupled orcommunicating through some interface, device, or intermediate component,whether electrically, mechanically, or otherwise. Other examples ofchanges, substitutions, and alterations are ascertainable by one skilledin the art and may be made.

While the above detailed description has shown, described, and pointedout the fundamental novel features of the disclosure as applied tovarious implementations, it will be understood that various omissions,substitutions, and changes in the form and details of the systemillustrated may be made by those skilled in the art. In addition, theorder of method steps is not implied by the order they appear in theclaims.

When messages are sent to/from an electronic device, such operations maynot be immediate or from the server directly. They may be synchronouslyor asynchronously delivered, from a server or other computing systeminfrastructure supporting the devices/methods/systems described herein.The foregoing steps may include, in whole or in part,synchronous/asynchronous communications to/from thedevice/infrastructure. Moreover, communication from the electronicdevice may be to one or more endpoints on a network. These endpoints maybe serviced by a server, a distributed computing system, a streamprocessor, etc. Content Delivery Networks (CDNs) may also provide mayprovide communication to an electronic device. For example, rather thana typical server response, the server may also provision or indicate adata for content delivery network (CDN) to await download by theelectronic device at a later time, such as a subsequent activity ofelectronic device. Thus, data may be sent directly from the server, orother infrastructure, such as a distributed infrastructure, or a CDN, aspart of or separate from the system.

Typically, storage mediums can include any or some combination of thefollowing: a semiconductor memory device such as a dynamic or staticrandom access memory (a DRAM or SRAM), an erasable and programmableread-only memory (EPROM), an electrically erasable and programmableread-only memory (EEPROM) and flash memory; a magnetic disk such as afixed, floppy and removable disk; another magnetic medium includingtape; an optical medium such as a compact disk (CD) or a digital videodisk (DVD); or another type of storage device. Note that theinstructions discussed above can be provided on one computer-readable ormachine-readable storage medium, or alternatively, can be provided onmultiple computer-readable or machine-readable storage media distributedin a large system having possibly plural nodes. Such computer-readableor machine-readable storage medium or media is (are) considered to bepart of an article (or article of manufacture). An article or article ofmanufacture can refer to any manufactured single component or multiplecomponents. The storage medium or media can be located either in themachine running the machine-readable instructions, or located at aremote site from which machine-readable instructions can be downloadedover a network for execution.

In the foregoing description, numerous details are set forth to providean understanding of the subject disclosed herein. However,implementations may be practiced without some of these details. Otherimplementations may include modifications and variations from thedetails discussed above. It is intended that the appended claims coversuch modifications and variations.

The invention claimed is:
 1. A method at a vehicle for refuelingsecurity, the method comprising: providing a short-range communicationchallenge from a reader associated with the vehicle to a short-rangecommunications module associated with a refueling station, the challengecomprising a random number; receiving a response from the short-rangecommunications module at the reader associated with the vehicle, theresponse comprising an electronic signature of the random number basedon a private key; comparing the response received at the reader with anexpected response, the comparing comprising verifying the electronicsignature of the random number with a public key; and determining thatthe response received matches the expected response and opening a fuelport on the vehicle.
 2. The method of claim 1, wherein the short-rangecommunication challenge is a near-field communication challenge.
 3. Themethod of claim 1, wherein the short-range communications module isassociated with an attendant at the refueling station.
 4. The method ofclaim 1, wherein the short-range communications module is associatedwith a fuel nozzle at the refueling station.
 5. The method of claim 1,wherein the short-range communications challenge comprises informationbased on codes exchanged between the vehicle and refueling station. 6.The method of claim 1, wherein the vehicle is an autonomous vehicle. 7.The method of claim 1, wherein the reader is on or around the fuel porton the vehicle.
 8. The method of claim 1, wherein the fuel port is atleast one of: a gasoline refueling port; a diesel refueling port; and anelectric vehicle charging port.
 9. A computing device associated with avehicle for refueling security, the computing device comprising: aprocessor; and a communications subsystem, wherein the computing deviceis configured to: provide a short-range communication challenge from areader associated with the vehicle to a short-range communicationsmodule associated with a refueling station, the challenge comprising arandom number; receive a response from the short-range communicationsmodule at the reader associated with the vehicle, the responsecomprising an electronic signature of the random number based on aprivate key; compare the response received at the reader with anexpected response, the comparing comprising verifying the electronicsignature of the random number with a public key; and determine that theresponse received matches the expected response and open a fuel port onthe vehicle.
 10. The computing device of claim 9, wherein theshort-range communication challenge is a near-field communicationchallenge.
 11. The computing device of claim 9, wherein the short-rangecommunications module is associated with an attendant at the refuelingstation.
 12. The computing device of claim 9, wherein the short-rangecommunications module is associated with a fuel nozzle at the refuelingstation.
 13. The computing device of claim 9, wherein the short-rangecommunications challenge comprises information based on codes exchangedbetween the vehicle and refueling station.
 14. The computing device ofclaim 9, wherein the vehicle is an autonomous vehicle.
 15. The computingdevice of claim 9, wherein the reader is on or around the fuel port onthe vehicle.
 16. The computing device of claim 9, wherein the fuel portis at least one of: a gasoline refueling port; a diesel refueling port;and an electric vehicle charging port.
 17. A non-transitory computerreadable medium for storing instruction code for refueling security,which when executed by a processor of a computing device associated witha vehicle cause the computing device to: provide a short-rangecommunication challenge from a reader associated with the vehicle to ashort-range communications module associated with a refueling station,the challenge comprising a random number; receive a response from theshort-range communications module at the reader associated with thevehicle, the response comprising an electronic signature of the randomnumber based on a private key; compare the response received at thereader with an expected response; and determine that the responsereceived matches the expected response and open a fuel port on thevehicle, the comparing comprising verifying the electronic signature ofthe random number with a public key.